I'd probably prefer for us to just leave the logic in the method itself.

fair enough

This block looks confusing as it currently stands.

Can't it just be...

try:
    queryset = view.get_queryset()
except AttributeError:
    queryset = getattr(view, 'queryset', None)

Or am I missing something?

The problem is that yo can have .get_queryset() defined but its implementation might raise AttributeError during execution. We should prevent catching this AttributeError.

but its implementation might raise AttributeError during execution.

That's such a crazy edge case that I don't really care about it. I'd prefer clarity of this code, and we'd still be using sensible enough behavior in that case. (Plus we'd expect the error to be raised elsewhere such as when initially using the queryset in the view)

I understand. I'm going to make the change

I'm not sure why we have an AssertionError block here, but it looks wrong. Just the first four lines are sufficient:

try:
    queryset = view.get_queryset()
except AttributeError:
    queryset = getattr(view, 'queryset', None)

Mainly for two reasons:
1 - To honour getattr(view, '_ignore_model_permissions', False) behaviour. Since some views without .queryset are tolerated.
2 - Because the absence of queryset is raised few lines below with an adhoc error message.

assert queryset is not None, (
    'Cannot apply DjangoModelPermissions on a view that '
)

I thought it would be nice to keep it that way, to be consistent with DjangoModelPermissions

We def don't need the AssertionError catching in either case, but it might also be nicer to move if getattr(view, '_ignore_model_permissions', False): return True behavior to instead be above the queryset check.

Very nice. I like it.